Repository navigation
Fix deployment stack What-If create/delete configuration rendering - #30268
anamikapan11 wants to merge 5 commits into
Conversation
|
Thank you for your contribution anamikapan11! We will review the pull request and get back to you soon. |
There was a problem hiding this comment.
🟢 Approval recommended
The focused implementation matches the stated behavior and linked Azure CLI change, with comprehensive regression coverage.
0 open findings
What changed in this PR
Aligns deployment stack What-If create/delete rendering with Azure CLI behavior.
Changes:
- Renders filtered
after/beforeresource configurations. - Preserves delta fallback and adds regression coverage.
- Updates repository and module changelogs.
| File | Description |
|---|---|
ChangeLog.md |
Records the Az.Resources improvement. |
src/Resources/Resources/ChangeLog.md |
Adds module release notes. |
src/Resources/ResourceManager/Formatters/DeploymentStackWhatIfFormatter.cs |
Implements configuration selection, filtering, and ordering. |
src/Resources/Resources.Test/Formatters/DeploymentStackWhatIfFormatterTests.cs |
Covers rendering, filtering, fallback, and potential changes. |
🧠 Review effort: Balanced
Give feedback about Copilot approvals in this survey to enter a drawing for a $150 gift card.
|
/azp run |
|
Azure Pipelines: Successfully started running 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
|
/azp run |
|
Azure Pipelines: Successfully started running 3 pipeline(s). |
Updated documentation for upcoming release with changes to improved deployment stack output rendering Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
|
/azp run |
|
Azure Pipelines: Successfully started running 3 pipeline(s). |
X Engineering Agent Report⏳ In progress — X Engineering Agent is reviewing this PR at Review — Comments The create/delete formatter selects the appropriate Before/After configuration, retains meaningful top-level values, and places properties last. Author-added tests in The earlier Copilot release-note concern is no longer present at this head: the Resources changelog contains the formatter entry, not an unrelated Test validation
Risk assessment — 17/100 · Low · High confidenceThe Low rating is driven by public CLI behavior.
Posted by x-engineering-agent (Reviewer) |
There was a problem hiding this comment.
anamikapan11 Ready for human review. See the X Engineering Agent Report.

🤖 PR Validation —⚠️ Review suggested
️✔️Az.Accounts
️✔️Az.KeyVault
️✔️Az.ManagedServiceIdentity
️✔️Az.Monitor
️✔️Az.Network
Description
Fixes https://dev.azure.com/msazure/One/_workitems/edit/40060008
Aligns deployment stack What-If configuration rendering with Azure/azure-cli#34156.
Changes
afterfor Create andbeforefor Delete, including potential changes.propertieslast.Validation
git diff --checkpassed.Scope
Mandatory Checklist
Please choose the target release of Azure PowerShell. (??????Target release is a different concept from API readiness. Please click below links for details.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the following information:ChangeLog.mdfile(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.## Upcoming Releaseheader in the past tense.ChangeLog.mdif no new release is required, such as fixing test case only.